Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

increases exxecution speed of CAS FM, number is up for a debate #5571

Closed

Conversation

cuberound
Copy link
Contributor

@cuberound cuberound commented Jan 27, 2024

About the pull request

reduces time betwean FM execution steps, increses it speed from 3 tiles per second to 5 tiles per second

Explain why it's good for the game

after I added all the extra warnings it is near imposible to hit xeno with it, especily considering that even when the xeno is in the area where the CAS is being fired, the FM moves so slowly that even the slowest xenos can outrun it easily , this aims to make CAS more powerful (and also cool looking), by making it move faster so that when you end up in the area where the CAS is being fired at even after all the warnings, you can not just walk away from it without getting hit, still have chance when you are close to edge of the FM

Testing Photographs and Procedure

Screenshots & Videos

Put screenshots and videos here with an empty line between the screenshots and the <details> tags.

Changelog

🆑
balance: increseas FM movement speed to 5 tiles per second from 3 tiles per second
/:cl:

@cuberound cuberound requested a review from fira as a code owner January 27, 2024 13:35
@github-actions github-actions bot added the Balance You need to be a professional veteran game maintainer to comprehend what is being done here. label Jan 27, 2024
@Drulikar
Copy link
Contributor

I don't think this solves the issue caused by the drastically increased amount of warning. You can book it even if you don't know where it is. I was hopeful sometimes people would be warned when they aren't close to it and then run closer to it sometimes but we also made the 2nd warning earlier too.

But tinker with things by testing locally with two clients.

@mullenpaul
Copy link
Contributor

Should this instead be a var on the weapons console that could be edited via VV? This would allow for more detailed experimentation rather than lots of back and forth testing. It would allow us to run an 'event' round where we pin the execution speed to a new number and see what we think. This would allow for general feedback from both xenos and marines

Copy link
Contributor

github-actions bot commented Feb 6, 2024

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

@github-actions github-actions bot added the Stale beg a maintainer to review your PR label Feb 6, 2024
@Drulikar Drulikar marked this pull request as draft February 6, 2024 21:48
@github-actions github-actions bot closed this Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Balance You need to be a professional veteran game maintainer to comprehend what is being done here. Stale beg a maintainer to review your PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants